Event rfid timing system and method having integrated participant event location tracking

ABSTRACT

A system and method for determining and tracking a location of a participant traveling along a route wherein the participant being tracked with an RFID tag using an RFID tag reader and a timing system, the system includes a location device associated with the RFID tag and has a location data receiver for receiving location information from a location providing source, and a wireless communication interface and time stamps each received location information, and transmits tag location data over the wireless interface, and a location detection device that is in wireless communication with the location device receives the transmitted tag location data, and transmits the received location data to the timing system, with the timing system associating the received location data with the RFID tag number as provided by the RFID tag reader provided tag reads of the RFID tag associated with the location device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/343,594 filed on Nov. 4, 2016, which is a continuation of U.S.National Stage application Ser. No. 13/980,545 filed on Jul. 18, 2013,which issued as U.S. Pat. No. 9,489,552, which claimed priority toInternational Application No. PCT/US2012/022132 filed Jan. 20, 2012,which claims the benefit of U.S. Provisional Application No. 61/434,782filed on Jan. 20, 2011, the disclosures of which are incorporated hereinby reference.

FIELD

The present disclosure relates to an event timing system and, morespecifically, to an event timing system including a location trackingsystem for tracking the timed participant or object throughout the timedevent.

BACKGROUND

The statements in this section merely provide background informationrelated to the present disclosure and may not constitute prior art.

When using an RFID system or similar detection technology system fortiming sporting events, it often desirable to track the progress of aparticipant. In current systems such as those used in marathons, an RFIDtag reader is setup at the beginning or starting line, and one or moremid-points was waypoints such as at various distance location along theroute of the marathon. Another final RFID tag reader is located at thefinish line to provide the determination of the participant's time fortraversing the marathon course.

Other systems, not used in current sport timing events, can track alocation of an objection by using a GPS receiver that receives geodeticlocation data from a plurality of orbiting GPS or GIS satellites. TheseGPS receivers are often used in vehicles and can be handheld, but arenot designed or suitable for use in most timed events such as runningraces. Furthermore, these GPS receivers often know their own locationwithin a certain accuracy, and have been implemented in modern smartphone technology. These smart phones include a GPS receiver and can beprogram with software programming in an “app” for providing locationdata via the application to remote systems. However, the carrying anduse of smart phones are not practical for use by event participants,especially where harsh conditions or water are present. Furthermore,these smart phones are not adaptable for use by a participant or anevent organizer for integration with event timing systems and arethemselves not accurate enough to be used for determining a participantsevent time.

As such, the inventor hereof has identified a need for a timing systemhaving and RFID tag reader capability for identifying each eventparticipant and for determining an accurate determination of theparticipants time in an event, but also that it would be desirable toobtain location data about each participant so that the progress of eachparticipant can be monitored, tracked and displayed to remote systemssuch as remote displays.

SUMMARY

The inventor hereof has succeeded at designing systems and methods forcapturing timed geographic location data of one or more moving objectsuch as participants along a timed event route or course, associatingsuch location data with each such object or participant, communicatingthe captured timed geographic location data to a timing system duringsuch an event for monitoring, tracking, reporting and displaying of thelocation and movement of the object or event in near real time during anevent and for having such location data for use after such an event.

According to one aspect, a system is provided for determining andtracking a location of a participant traveling along a route wherein theparticipant being tracked with an RFID tag during an event. The systemincludes a tag reader system receiving one or more tag reads from theRFID tag, determining a time for each tag read, identifying the tagnumber of the RFID tag, and transmitting a tag read message including atleast a portion of the received tag reads with the tag number and thedetermined times. A timing system is configured for receiving andstoring the tag read message including the tag number from the tagreader. A location device that is associated with the RFID tag of theparticipant has a location data receiver for receiving location datafrom a location providing source, and a wireless communicationinterface. The location detection device receives location informationfrom the location providing source, time stamps each received locationinformation, and transmits tag location data over the wirelessinterface. A location detection device that is in at least periodicwireless communication with the location device receives the transmittedtag location data, and transmits the received location data to thetiming system. The timing system stores the location data and associatesthe location data with the RFID tag number as provided by the RFID tagreader from at least one of the tag reads from the tag associated withthe location device.

In another aspect, a timing system is provided for determining andtracking a location of a participant traveling along a route wherein theparticipant being tracked with an RFID tag during an event. The systemincluding a tag reader system having a processor, a memory, a clock, acommunication interface for communicating with a timing system, a radiofrequency transceiver for wirelessly communicating with the tag forreceiving a tag identification unique to the tag, and one or moreantenna coupled to the radio frequency transceiver that are positionedat a first monitored point at a first distance from the reference line,the tag reader system transmitting a tag read request and receiving oneor more tag reads from the tag, and transmitting over the communicationinterface a tag read message including at least a portion of thereceived tag reads; a timing system having a processor, a memory, and adata interface, the timing system receiving and storing the tag readmessage including the tag identification from the tag reader,determining whether a tag location device is associated with the tagidentification, and if so, transmitting a location data request commandincluding the tag identification; the tracked location device having alocation data receiver, a processor, a clock and a wirelesscommunication interface, the location detection device receivinglocation information on a periodic basis from a location providingsource and time stamping each receiving or determined location aslocation data, receiving a request for wirelessly transmitting thelocation data; and transmitting the location data responsive to thereceived request; and a location detection device having a processor, amemory, a wireless communication interface for communicating with thetracked location device, and a data communication interface forcommunicating with the timing system, the location detection systemtransmitting the request for the location data responsive to receiving acommand from the timing system including the tag identification, andreceiving the location data from the tracked location device associatedwith the tag identification, and forwarding the received location datato the timing system, wherein the timing system stores the location dataand associated the location data with the tag read message including thetag identification.

In yet another aspect, a method for determining and tracking a locationof a participant traveling along a route wherein the participant beingtracked with an RFID tag during an event. The method including in a tagreader system the processes of receiving one or more tag reads from theRFID tag, determining a time for each tag read, identifying the tagnumber of the RFID tag, and transmitting a tag read message including atleast a portion of the received tag reads with the tag number and thedetermined times. The method also including in a timing system, theprocesses of receiving the tag read messages as transmitted by the tagreader system and storing the tag read message including the tag numberfrom the tag reader. The method including in a location deviceassociated with the RFID tag of the participant, the processes ofreceiving location data from a location providing source, time stampingeach received location information; and transmitting tag location dataover the wireless interface. In a location detection device in at leastperiodic wireless communication with the location device, the processesof receiving the transmitted tag location data; and transmitting thereceived location data to the timing system. In the timing system,receiving the location data, associating the location data with the RFIDtag number as provided by the RFID tag reader from at least one of thetag reads from the tag associated with the location device; and storingthe location associated with the RFID tag number.

Further aspects of the present disclosure will be in part apparent andin part pointed out below. It should be understood that various aspectsof the disclosure may be implemented individually or in combination withone another. It should also be understood that the detailed descriptionand drawings, while indicating certain exemplary embodiments, areintended for purposes of illustration only and should not be construedas limiting the scope of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of a typical TS system configurationthat is used to read a Race Bib Tag as it passes antennas that aremounted overhead and on the side of a racecourse. The specific locationof the antennas could be changed to include any position that is deemedsuitable for receiving the Bib Tag signal from the tag according to oneexemplary embodiment.

FIG. 2 is a schematic drawing showing a redundant TS Detection Systemnetwork configuration according to one exemplary embodiment. accordingto a first exemplary embodiment.

FIG. 3 is a schematic drawing showing a detection point along aracecourse having an RFID tag reader supplemented with a locationdetection system (LDS), according to one exemplary embodiment.

FIG. 4 is schematic block diagram of an architecture and communicationsystem for a timing system (TS) coupled via a timing systemcommunication network (TS NET) for obtaining, storing and processing ofparticipant location data as obtained during an event and the providingof such location data to coupled systems, according to one exemplaryembodiment.

FIG. 5 is a flow chart of a process for integrating a location tag withan RFID tag for a participant in an event and the reading of the RFIDtag and the location tag during the event as the participant traversesthe event course R at numerous location detection points along course Raccording to one exemplary embodiment.

FIG. 6 is an illustration of an event court R wherein multiple locationdetection points provide for the near real time providing of locationdata to an integrated RFID tag reading timing system according to oneexemplary embodiment.

FIG. 7 is an illustration of a webpage display of the of a displaysystem for displaying in near real time the location, monitoring andtracking of a participant in an event according to one exemplaryembodiment.

FIG. 8 is a block diagram of a second participant's tag (PT) having anRFID timing chip (TA) and a location detection chip (LA) and thewireless interfaces between the external components of a timing systemaccording to one exemplary embodiment.

FIG. 9 is a block diagram of a third participant's tag (PT) having aRFID timing chip (TA) with an integrated location detection chip (LA)and a timing system having an integrated RFID tag reader and taglocation detection system according to one exemplary embodiment.

FIG. 10 is a block diagram of a specialized computer system suitable forimplementing one or more assembly or methods of various embodiments asdescribed herein.

It should be understood that throughout the drawings, correspondingreference numerals indicate like or corresponding parts and features.

DETAILED DESCRIPTION

The following description is merely exemplary in nature and is notintended to limit the present disclosure or the disclosure'sapplications or uses.

In one embodiment, a system 100 as shown in FIGS. 1 and 2 is providedfor determining and tracking a location of a participant 110 travelingalong a route R 114 wherein the participant 110 being tracked with anRFID tag 108 during an event. The system 100 includes a tag readersystem 104 receiving one or more tag reads from the RFID tag 108,determining a time for each tag read, identifying the tag number of theRFID tag 108, and transmitting a tag read message including at least aportion of the received tag reads with the tag number and the determinedtimes. A timing system 102 is configured for receiving and storing thetag read message including the tag number from the tag reader 104.

As shown in FIG. 3, the system 300 can also include a location device130 that is associated with the RFID tag 108 of the participant 110 hasa location data receiver for receiving location data from a locationproviding source 132, and a wireless communication interface. Thelocation providing source 132 can be one or more of a plurality of GPSsatellites 132 and wherein the location data LD is GPS data. Thelocation device 130 can include the RFID tag number of the associatedRFID tag 108 for the participant 110 and in some embodiment can beconfigured for storing location data at intervals based on apredetermined rate.

The location device 130 can be configured to receive programminginstructions for establishing the predetermined rate, and wherein suchpredetermined rate can be change with the receipt of new programminginstructions during an event. As shown in FIG. 9, the location device130 is communicatively coupled to the RFID tag 108 in the form of aparticipant tag (PT) 134.

In some embodiments, location device 130 is configured to receive a GPSdownload request, and wherein the location device 130 transmits the taglocation over the wireless interface to a location detection device 122responsive to said request. For instance, in some cases, at least one ofthe timing system 102 and the tag reader system 104 detects theproximity of the RFID tag 108 to the RFID tag reader 104 and transmits alocation data download command to the location detection system 120, andwherein the location detection device 122 transmits the GPS downloadrequest to the location device 130.

In some embodiments, the location detection device 122 only transmitsthe received location data responsive to the location detection device122 receiving an input that a transmission to the location detectiondevice 122 is currently available.

The location detection device 122 receives location information from thelocation providing source, time stamps each received locationinformation, and transmits tag location data over the wirelessinterface. A location detection device 122 that is in at least periodicwireless communication with the location device 130 receives thetransmitted tag location data, and transmits the received location datato the timing system.

The timing system stores the location data and associates the locationdata with the RFID tag number as provided by the RFID tag reader 104from at least one of the tag reads from the tag associated with thelocation device 130.

In some embodiments, the timing system is configured to transmit thelocation data associated with a particular RFID tag number responsive toa request from a remote system. For instance, a remote system can beconfigured to request location data from the timing system, receive therequested location data, and to display the location data on a displaymap of the route 114 indicating the route 114 traveled by theparticipant or the most recent and current location of the participant.As noted in FIG. 3, the remote system is a Kiosk 170, a website 172, amobile phone 174, a PC, a tablet 176, a news station, a third partyapplication 178, or a broadcast network 180.

In some embodiments, the location device 130 is configured for selectiveactivation and deactivation of its location data receiver 130, andwherein the wireless interface is configured to receive activation anddeactivation commands, and wherein the location detection system 120 isconfigured for transmitting the activation and deactivation commandsresponsive to a message received from the timing system 102.

In some embodiments, the location detection system 120 is configured totransmit to the location tag 108 a location data request requesting allor a portion of the location data from the location device 130, andwherein the location device 130 is configured to transmit the locationdata LD responsive to the location data request.

In some embodiments, the location detection system 120 is configured totransmit a dump all data and then clear all data commands, and whereinthe location device 130 is configured to transmit all of the locationdata and then clear a memory associated with the location device 130.

In another embodiment, a timing system 102 is provided for determiningand tracking a location of a participant 110 traveling along a route 114wherein the participant 110 being tracked with an RFID tag 108 during anevent. The system 100 including a tag reader system 104 having aprocessor, a memory, a clock, a communication interface forcommunicating with a timing system, a radio frequency transceiver forwirelessly communicating with the tag 108 for receiving a tagidentification unique to the tag 108, and one or more antenna 106coupled to the radio frequency transceiver that are positioned at afirst monitored point 112 at a first distance from the reference line,the tag reader system 104 transmitting a tag read request and receivingone or more tag reads from the tag 108, and transmitting over thecommunication interface a tag read message including at least a portionof the received tag reads; a timing system 102 having a processor, amemory, and a data interface, the timing system 102 receiving andstoring the tag read message including the tag identification from thetag reader 104, determining whether a tag location device 130 isassociated with the tag identification, and if so, transmitting alocation data request command including the tag identification; thetracked location device 130 having a location data receiver, aprocessor, a clock and a wireless communication interface, the locationdetection device 122 receiving location information on a periodic basisfrom a location providing source 132 and time stamping each receiving ordetermined location as location data LD, receiving a request forwirelessly transmitting the location data LD; and transmitting thelocation data LD responsive to the received request; and a locationdetection device 122 having a processor, a memory, a wirelesscommunication interface for communicating with the tracked locationdevice 130, and a data communication interface for communicating withthe timing system, the location detection system 120 transmitting therequest for the location data LD responsive to receiving a command fromthe timing system 102 including the tag identification, and receivingthe location data LD from the tracked location device 130 associatedwith the tag identification, and forwarding the received location dataLD to the timing system 102, wherein the timing system 102 stores thelocation data LD and associated the location data LD with the tag readmessage including the tag identification.

In another embodiment, a method for determining and tracking a locationof a participant 110 traveling along a route 114 wherein the participant110 being tracked with an RFID tag 108 during an event. The methodincluding in a tag reader system 104 the processes of receiving one ormore tag reads from the RFID tag 108, determining a time for each tagread, identifying the tag number of the RFID tag 108, and transmitting atag read message including at least a portion of the received tag readswith the tag number and the determined times. The method also includingin a timing system 102, the processes of receiving the tag read messagesas transmitted by the tag reader system 104 and storing the tag readmessage including the tag number from the tag reader 106. The methodincluding in a location device 130 associated with the RFID tag 108 ofthe participant 110, the processes of receiving location data LD from alocation providing source 132, time stamping each received locationinformation; and transmitting tag location data LD over the wirelessinterface. In a location detection device 122 in at least periodicwireless communication with the location device 130, the processes ofreceiving the transmitted tag location data; and transmitting thereceived location data to the timing system. In the timing system,receiving the location data, associating the location data with the RFIDtag number as provided by the RFID tag reader 104 from at least one ofthe tag reads from the tag associated with the location device 130; andstoring the location associated with the RFID tag number.

In some embodiments, the location device 130 stores of location data isat intervals based on a predetermined rate. The location device 130 canbe programmed to receiving programming instructions for establishing thepredetermined rate as well as other data and operations. Thepredetermined rate can be changed with the receipt of new programminginstructions during an event. As another example, the location device130 can receive GPS download request, and then transmit the tag locationover the wireless interface to a location detection device 122 isresponsive to said request. In some embodiments, either timing system orthe tag reader system uses the RFID tag reads to detect a proximity ofthe RFID tag 108 to the RFID tag reader 104 and then transmits alocation data download command to the location detection system 120. Insuch embodiments, the location detection device 122 transmits the GPSdownload request to the location device 130. In some embodiments, thelocation detection device 122 only transmits responsive to the locationdetection device 122 receiving an input that a transmission to thelocation detection device 122 is currently available.

As noted above, where there is a coupled remote system, the remotesystem can request the location data from the timing system 102 andreceiving the requested location data. Once received, the location dataLD can be displayed on a display map of the route 114 indicating theroute 114 traveled by the participant 110 or the most recent and currentlocation of the participant 110.

In another embodiment, location detection system 120 transmits at leastone of an activation and a deactivation command responsive to a messagereceived from the timing system 102 and the location device 130selectively activates and deactivates the location data receiver 130responsive to receipt of the message from the location detection system120.

In another embodiment, the location detection system 120 transmits tothe location tag 130 a location data request requesting all or a portionof the location data LD from the location device 130, and the locationdevice 130 transmits the location data LD responsive to the locationdata request.

In another embodiment, the location detection system 120 transmits adump all data command and then transmits a clear all data command. Insuch embodiments, the location device 130 transmits all of the locationdata LD responsive to the receipt of the dump all data command andclears a memory of all location data LD responsive to receiving theclear all data command.

According to one embodiment, a timing system 102 for determining a timeof a passing at a reference line 112 of a tracked tag 134 associatedwith an object/participant traveling along a route 114 and capturing animage of such passing and integrating the captured image with thedetermined time for the tracked tag, the system 100 comprising a tagreader system 104, a timing system 102, a tracked location device 134and a location detection system 120.

In some embodiments, the tag reader system 104 has a processor, amemory, a clock, a communication interface for communicating with atiming system 102, a radio frequency transceiver for wirelesslycommunicating with the tag 108 for receiving a tag identification uniqueto the tag 108, and one or more antenna 106 coupled to the radiofrequency transceiver that are positioned at a first monitored point ata first distance from the reference line 112, the tag reader system 104transmitting a tag read request and receiving one or more tag reads fromthe tag 108, and transmitting over the communication interface a tagread message including at least a portion of the received tag reads.

In some embodiments the timing system 102 has a processor, a memory, anda data interface, the timing system 102 receiving and storing the tagread message including the tag identification from the tag reader 104,determining whether a tag location device 130 is associated with the tagidentification, and if so, transmitting a location data request commandincluding the tag identification.

In some embodiments the tracked location device 130 has a location datareceiver 122, a processor, a clock and a wireless communicationinterface, the location detection device 122 receiving locationinformation on a periodic basis from a location providing source 132 andtime stamping each receiving or determined location as location data LD,receiving a request for wirelessly transmitting the location data LD;and transmitting the location data LD responsive to the receivedrequest. In some embodiments, the location detection device 122 has aprocessor, a memory, a wireless communication interface forcommunicating with the tracked location device 130, and a datacommunication interface for communicating with the timing system 102,the location detection system 120 transmitting the request for thelocation data LD responsive to receiving a command from the timingsystem 102 including the tag identification, and receiving the locationdata LD from the tracked location device 130 associated with the tagidentification, and forwarding the received location data LD to thetiming system 102, wherein the timing system 102 stores the locationdata LD and associated the location data LD with the tag read messageincluding the tag identification.

The TS LDS 120 enables an object or a participant 110 to wear a smalllightweight location tracking device or tracked location device 130 (LA)such a GPS receiver, cellular triangulation receiver, cell phone or thelike, while traveling a predetermined course or timed track 114. The TSLDS 120 will store location data points every 1, 5, 10, or 30 seconds asdetermined by the user. The location data (LD) is collected from up to 8satellites that the LA receiver 130 may lock onto when the user 110 iswearing the device 130. The LA device 130 has memory that is capable ofstoring thousands of location data points such that a user couldparticipate in a Marathon or perhaps a Triathlon that lasts for hours.The LA 130 operates on a small battery or other power source or canutilize power conservation as will be described below. As the LA tag 130for each participant 110 comes within a wireless range of a LocationDetection System 120 (LDS) that may or may not be equipped with an RFIDtag reader 104 (TRS) for reading the 5 to 10 feet of a TS 102 componentsuch as TRS 104 equipped with a LDS 120, the location data LD isrequested or otherwise transmitted from the participants LA tag 130 tothe local LDS 120, and subsequently to either the coupled TRS 104 ordirectly to the TS 102 via the TS NET 140, as shown in FIG. 4. The LA130 and LDR 122 communicate data and protocol messages, such asdescribed below, via any suitable wireless technology such as Wi-Fi, byway of example, but not intending to be limited thereto. The TRS 104with LDS 120 or standalone LDS 120 systems can also collect the RFIDchip read 108 wherein the LD can be associated with the particularparticipant 110 and verified as such. However, in addition to the chipread, the TS 102 can collect operating as a data collection point forthe GPS tracking information. Once the LA 130 of the participant 110 hastransmitted its location data LD that it has collected during the travelof the participant 110 along the event course R 114, the memory of theLA chip 130 can be retained, marked as sent, or can be cleared. Forexample, a race even organizer may implement five timing systems 102along a course R 114 with each positioned or spaced apart around courseR 114 for gathering participant location data LD during or apart fromRFID tag reads TD. As location data LD is collected by the LDS 120 orTRS 104 with LDS 120 systems, the LD can be transmitted to theresponsible TS system 102 for storing and further processing. Displayand remote systems coupled to the TS 102, can be provided with thecollected LD on a participant basis, during and following the event. Forexample, during the event, the LD representing the location and progressof a particular participant 110 can be sent from the TS 102 totelevision screens so that event spectators can see the location andprogress of a participant 110 such as by requesting a query from the TS102. In other cases, a remote system or user can subscribe or request LDfor one or more participants 110, so that they can track, monitor, anddisplay the location and progress locally. These remote systems caninclude, but are not limited to, news and broadcast agencies 180,webpages 172, mobile phones 174 and tablets, or event participantdatabases 706 that collect participant data for analysis or otherpurposes.

The presently disclosed system 100 provides a timing system 102 and theuser of such system the ability to collect the location data LD on asmall device associated with the participant 110, and then wirelesslytransmit that location data LD to the location data detection orcollection systems (LDS) 120 stations along an event course. Inaddition, the disclosed communication protocol enables the TS system 102to receive such participant location data LD, and to provide or makeavailable such location data to users and/or systems desiring suchparticipant location data.

In another embodiment, a Location Tracking device or tracked locationtag device (LA) 130 has a GPS or other location receiver (could becellular triangulation or the like such as a local system) withcorresponding first antenna; a process; a memory; computerinstructions/software with a database or data storage format; a battery;a housing possibly with an on-off switch, an indicator LED for uservisual on or low battery indicator; a second antenna; and a wirelesstransceiver coupled to the second antenna, and operating at apredetermined wireless operating parameters (frequency, protocol, etc.).The LA 130 regularly receives timing signal, (may be an externalGPS/location signal in one embodiment if such were available to thisunit), receives/determines a plurality of time stamped location data LDof the participant 110, e.g. TSLD 120 including the LsubNs, time stampsthem, and stores them in the memory. Each LA also includes a LAIdentification data that is transmitted with each for uniquelyidentifying the LA and possibly participant data or identification, etc.

In some embodiments, the LDS 120 includes interfaces each having anantenna and a wireless transceiver coupled thereto and beingcommunicative with the LA wireless transceiver (compatible operatingparameters). The Interface consistently transmitting a read request forrequesting a transmission from any LA 130 within the wireless range ofthe LT TS Interface. The Interface receiving the data including at leasta portion of the TSLD data. Could be all or that which is new since thelast read or a clean dump each time. The wireless transceiver is alwayson for detecting a read request from a LT TS Interface. The LTTSItransmits the received TSLD to a TS 102.

In some embodiment the TS 102 receives the LDS 120 received locationdata including the LA ID/Participant ID and stores the LD in a memoryfor each participant. The TS system 102 formats the LD data for eachparticipant 110. The TS system 102 includes an API with a protocol thathas a Request LD message that includes a participant ID and can respondwith a Provide LD message that includes the TSLD data with theparticipant ID to the requesting entity.

When a chip is read along the course, we then send out a message to theGPS unit to dump it's memory to us over a packet protocol we havedesign. The packet is actually quite simple because we don't want muchoverhead given that the person running by isn't within view for long.

Another exemplary embodiment process/method:

a. RFID Tag/Chip read occurs on the RFID tag by the tag reader detectionsystem (DS). Once this RFID tag is read, the TS 102 determines the tagID of the object or participant that is approaching the detection point(DP) 112 that is equipped with a LDS 120, such as 50 to 75 feet beforethe actual DP 112.

b. The TS 102 notifies the LDS 120 of the approaching tag number, andthe LDS system 120 communicates with the LA 130 for that approachingparticipant 110. The window for this can be between 3 to 10 seconds in atypically running timed event where a short-range low power wirelesstechnologies is used for communication between the LDS 120 and the LA130.

c. The TS LDS 120 issue a request (JGPREQ) to the LA 130 of the objectusing the tag id in the request. This request can be to have the LA 130transmit all timed location data points within its memory back to therequesting TS LDS 120.

d. After the TS LDS 120 receives the requested location data from theaddressed LA, the TS 102 can send a Clear Memory command to free up thememory in the GPS unit. (JGPCLM) or if on a portion need to be cleared acommand with a percent indicator (JGPCLMXX) where XX represents thepercentage of memory to clear, starting with the oldest records inmemory. This is useful if the operator wants to only clear the first setof records that have been read by perhaps 2 or 3 stations earlier alongthe course. By having a rolling memory clear, we can ensure that the LAunit 130 is read by multiple stations and we are clearing out the oldestdata periodically to make room for the new information being gathered.

A Requesting Entity (RE) is coupled to the TS 102 via a datacommunications network 140 using a protocol as described herein. Therequesting entity can be a Kiosk 170 or an Announcer and the app sendsthe request and then processes the received Provide TSLD message anddata for various uses such as a display on a map of the event, ortransmitting such or display on a GUI etc.

Referring to FIG. 3, a schematic drawing showing a detection point 112along a racecourse 114 having an RFID tag reader 104 supplemented with alocation detection system 120 (LDS), according to one exemplaryembodiment is illustrated showing the participant 110 with a TA/LAparticipant tag 134 having the RFID tag 108 (TA) and the location tag LA130 the location tag LA 130 receives the GN location data from the GPSsatellites 132. As the runner PA 110 approaches the monitored point MP112 having the tag reading system TRS 104 with the RFID device sensorsDS1 106, the RFID tag TA 108 of PA 110 is read and the RFID tag numberis sent to the TRS 104 and on to the TS 102. Upon receipt of the RFIDtag detection and in some cases the receipt of the particular RFID tagnumber, an instruction is sent to the LDS 120. The LDS 120 transmits alocation request message to the location tag LA 130. In reply the LA tag130 transmits its location data LD to the location data receivers LDR1122 or LDR2 122 that is associated with the LDS 120. The LDS 120 thantransmits the received location data LD to the TS 102. The TS 102associates the received location data LD with the RFID tag number of therequested read.

FIG. 4 depicts a schematic block diagram of a system 400 having anarchitecture and communication system for a timing system (TS) 102having memory 706 with tag reader 104 and location detection system 120that are communicatively coupled to location satellites 132 are coupledvia a timing system communication network (TS NET) 140 for obtaining,storing and processing of participant location data LD as obtainedduring an event and the providing of such location data LD to coupledsystems, according to one exemplary embodiment. In this embodiment, oneor more remote systems TS2 102 and participant registration system (PRS)142 are coupled to the TS 102. Each of these remote systems can send alocation data request message and receive the requested location data.Such remote site can also be preorder from a local participantregistration system (LRS) 144, as well as a kiosk 170, a website 172, acell phone 174, a tablet computer 176, a third party application 178 anda news feed 180.

Turning to FIG. 5, a flow chart of a process 500 for integrating alocation tag 130 with an RFID tag 108 for a participant 110 in an eventand the reading of the RFID tag 108 and the location tag 130 during theevent as the participant 110 traverses the event course R 114 atnumerous location detection points 112 along course R 114 according toone exemplary embodiment is illustrated. As shown in the flow chart, theTS 102 activates the RFID tag 108 in step 502 and then activates thelocation device 130 in step 504. The Location device 130 LA collectslocation data in step 506 as the Pa 110 traverses the route 114. In step508 an RFID reader 104 detects the presence of the RFID tag 108 andnotifies the TS 102 and or the LDS 120. The TS 102 or LDS 120 instructsthe location detection receiver system 122 to request that the locationdevice 130 provide its current location data. The location device 130downloads or transmits its location data LD to the TRS 104 in step 510.This process 500 continues as shown as the PA 110 traverses the coursewith additional RFID tag reads in step 512 and additional receipt of thedumped LD in step 514. At the end, when the PA 100 crosses the finishline 112, the last RFID tag reader 104 sees this and instructs thesystem 120 to dump all location data in step 516 and clear the locationdevice memory in step 518.

Referring to FIG. 6, an illustration 600 of an event court R whereinmultiple location detection points DPN (shown as DPA, DPB, DPC and DPD)provide for the near real time providing of location data LD to anintegrated RFID tag 108 reading timing system 102 according to oneexemplary embodiment is shown. As shown, as the participant PA 110traverses the route 114, multiple RFID tag 108 reads result in multiplelocation downloads from the location device 130, thereby providing theTS 102 with regular updates of the location data LD (shown as LD A1, LDA2, LD A3, LD B1, LD B2, and LD B3), for each monitored RFID tag 108with a location device 130. FIG. 7 illustrates a webpage display 700that is a possible remote system website 172 that requested the locationdata LD as illustrated in FIG. 6. As shown, this displays a graphicimage 702 of the illustrated tracking course 600 as in FIG. 6.

Referring now to FIG. 8, a block diagram of the relationship between aparticipant's tag (PT) 134 having an RFID timing chip (TA) 108 and alocation detection chip (LA) 130 and the wireless interfaces between theexternal components of a timing system 102 according to one exemplaryembodiment is shown. As shown here, the TA RFID tag 108 and the locationdevice 130 LA can be separate electronic devices within theparticipant's tag PT 134.

Turning to FIG. 9, a block diagram of a second participant's tag (PT)134 having an RFID timing chip (TA) 108 and a location detection chip(LA) 130 and the wireless interfaces between the external components ofa timing system according to one exemplary embodiment is depicted. Asdepicted here, the LA 130 and the TA 108 can be coupled as an integratedassembly 136 to form participants tag 134 as shown.

The TS NET system is suitable for use with the herein described STIIS isan event communication system that provides real-time statistics andevent participant information to computing devices, web sites, cellularphones, television displays and monitors, and other types ofcommunication devices. The capabilities of the TS NET system include,but are not limited to the following: (1) interfaces with existing TStiming systems to provide real-time updates of participant information,images and video, on television displays or monitors, (2) provides eventclock screens that can show the elapsed event time updated in real-time,(3) provides real-time updates of times on participants at any point onthe event course, (4) provides detailed event statistics which areupdated in real-time, (5) includes event reports including, but notlimited to, total finishers, total males, total females, top 5 malefinishers, and top 5 female finishers, (6) provides real-time updates toweb sites with event participant results, (7) includes searchcapabilities for locating individual or groups of participants within anevent, (8) provides the ability to generate custom messages for eventparticipants that are displayed as they cross a detection point on thecourse, (9) includes the ability to generate custom advertising messagesthat are shown on an event related display such as an event clock, and(10) provides data storage for event results which can be retrieved atany time during the event and (11) location data of the participant withtimings at each location.

When using a sport timing system (TS) using an integrated communicationsystem (TS NET) for timing participants in sporting event, the TS NETsystem and method makes it possible to view updated participantinformation including, but not limited to, finish times, bib numbers,and participant names on one or more large displays. The TS NET systemalso displays a real-time event clock display showing elapsed eventtime. In addition, the TS NET system provides a real-time update screenof event results that can be used by anyone who is providing eventupdates over a radio or television station, or who is providing updatesover a public address system at the event site. The displays supportedby the TS NET system include flat-panel television screens or monitorsthat are placed at a finish line or in an area where participants orspectators can see the results. The information displayed on the screensnot only includes participant results, it also includes custom messagesfor each participant, as well as advertising messages from eventsponsors. Messages and screen displays can be customized by the user toutilize various font sizes, font types, colors, and the placement ofinformation on the screens. Furthermore, the user can modify screenimages to include custom artwork and logos and that information willalso be displayed as event results are being updated on the televisionscreens or monitors. The TS NET system can also update a web site withevent results during the event, thus providing a communications tool forpublishing event information over the internet.

The TS NET system utilizes a network to receive messages coming from anTS that may have one or more tag reader or participant detection systemsassociated therewith. For example, an TS-TS NET communication systemenables the sharing of participant and event data among systems insupport of sport timing ancillary systems and applications. The TS NETsystem can receive messages from multiple systems. Thus, numerousdetection systems can be placed at many locations on an event course andinformation from those systems can be transmitted over a networkconnection to the TS NET system. The network interface for the TS NETsystem can use a connected or disconnected state-less connection, thusallowing guaranteed or non-guaranteed information delivery, such as aTS-TS NET network interface.

As described herein, an TS NET system utilizes a network to receiveformatted text messages coming from a sport timing system. There are twoprimary types of messages that can be used when communicating with theTS NET system. The first type of message provides the event participantinformation to the TS NET system. The second type of message providesfor time synchronization to make sure that the TS NET system is usingthe same time standard as used by the other TS and TS-TS NETcommunicating systems at the event. The message format for the TS NETsystem supports variable length messages that can be customized by theuser. The information can be transmitted via numerous technologiesincluding, but not limited to, wired networks, wireless networks,satellite networks, cellular networks, serial networks, or privatenetworks. The messages can be transmitted over any type of networkcommunications protocol including, but not limited to, TCP/IP or UDP, oras generally defined herein by way of example as TS-TS NET.

The TS NET system listens for messages on an IP address and socketnumber defined by the user in a configuration screen. Once this has beendone, the system listens on the designated IP address and socket forinbound messages. When a message is received, it is processed by TS NET.Depending on the configuration of the TS NET system, real-time displaysmay be formatted and updated with participant or event information. Inaddition, web site updates may be completed, and reports may be updated,email messages formatted and sent, text messages formatted and sent, andimages and videos transmitted and displayed by display devices.

The message type indicator at the beginning of the information packetdetermines the action taken by the TS NET system. Participant specificmessages will contain the ANNC indictor that contains participantdata/information. The end of each message or information packet shouldalways contain an end of message delimiter, for example, as describedherein an EOM “|” indicator to ensure that the end of packet can beidentified by the TS NET system. In addition, the “|” character shouldbe used to indicate the end of each field within the information packet.There are no limits on the length of a field within the informationpacket. Thus, the system can transmit a significant amount of event andparticipant information within a single message, and can include imageand video links or even files.

While the TS NET system was designed for sporting events, it could beused for any number of other applications that may be associated withmultiple detection systems having to work interactively together for acommon purpose. Furthermore, while the TS NET system will be describedin conjunction with the current embodiments, it will be understood thatthey are not intended to limit the TS NET system to these embodiments.On the contrary, the current design is intended to cover alternatives,modifications and equivalents, which may be included within the spiritand scope of the TS NET system.

The TS-TS NET interfaces can include a pair mated datagram messagesincluding a requesting and receiving location data.

In yet another embodiment, a method for communicating real-time sportingevent and participant announcement information received from a sporttiming system (TS), the method including receiving, at an announcementinterface system having a processor, a memory, a first data interfacecommunicating over the a stateless packet data communication networkwith the sport timing system, receiving a multicast datagram locationrequest and read messages including an identification of the sporttiming system and participant data including a participant identifierfor uniquely identifying each participant in the sporting event andparticipant timing data. The method also including formatting, in theannouncement interface system, the received portion of the participantdata into an announcement system message having a predetermined dataformat. The method further including transmitting, at a second interfaceof the announcement interface system communicating with an announcementsystem, the announcement system message including the participant data,the participant identifier, and participant timing data and theparticipant location data.

The TS-TS NET facilitates and streamlines the communication of tagreader or participant detection system timing information betweenmultiple computers used at sporting events. The protocol is flexible andadaptable and can be used to transmit any type of information across anytype of network. The use of variable length messages makes it possibleto customize the messages sent or received from any type of device. Theprotocol is simple and efficient and can be quickly implemented.

The foregoing descriptions of specific embodiments of the present designhave been presented for the purposes of illustration and description.They are not intended to be fully exhaustive or to limit the design tothe precise use, form, or methods disclosed, and it is obvious that manymodifications or variations are possible in the light of the informationprovided above. The embodiments were chosen, shown, and described inorder to best explain the concepts and principles and the practicalapplication of the design, thus providing others skilled in the art theability to best utilize the design and various embodiments with variousmodifications as are suited to the particular use desired.

The Timing System (TS) Interactive Communication System and Method(TS-TS NET) as described herein has both text files and networkinterface files.

TS-TS NET can have text files that a user or TS system developer canaccess for creating TS-TS NET compatible systems or applications.

In addition, a network interface provides an ability to communicate withan TS system such as TS NET in real-time using TS-TS NET. The fileinterface is very quick and easy to use. The network interface is muchmore complex and can require experience in writing network applications.In addition, as described herein one skilled in the art of this TS-TSNET network interface and method requires an understanding of anyoperating systems environments in which the present TS-TS NET system andmethod are implemented. As such, it is assumed that any person of skillin the art implementing the present TS-TS NET system and method is wellversed in such implementing operation system environment.

TS-TS NET can access multiple TS files that are used within one or moreof the multiple TS systems including the Chip or TS Output File and theTS Database File. The file formats documented below are subject tochange, so please check with us periodically for updates.

An TS system with a coupled participant detection system monitors adetection point and collects the identification of the detectedparticipant and stamps a time of detection for each participant. Theseare referred by way of example herein as collecting participant anddetection data including detection times, which can be written asparticipant read information to a text file. As described by way ofexample herein, a “chip” is a timing chip that is associated with aparticipant in the sporting event. A chip refers to the detection of atparticular participant by a particular detection system. While a chiprefers generally to an RFID chip and the reader is an RFID reader, thoseskilled in the art would understand that the reference to an RFID chipor chip, could be any type of tag reader or participant detection at adetection point and still be within the scope of the present disclosure.

An TS system or a user of such TS system can predetermine the name andlocation for the TS OUTPUT FILE. This file is updated in real-time bythe TS system as the event progresses and it contains the followinginformation: Antenna#,Bib#,Bib#,“Time” The file always uses a delimitedformat, shown here by example using commas as the delimiters, and thetime field can be any format, but is shown in this example as havingquote marks.

The exemplary format for the TS OUTPUT FILE is readable by a spreadsheetor many third party programs, but other formats are also possible. An TSsystem can ignore the Antenna # field for many applications as theAntenna# field is often used internally by an TS for uniquelyidentifying the actual equipment making the detection. The Bib # fieldappears twice and this is not an accident. This is repeated in thisexemplary embodiment as several third-party programs require this formatwhen importing an event timing data file. The final entry is the time ofthe chip read which is in the format of “HH:MM:SS” or “HH:MM:SS.XXX.” Asshown in this later example, the format for chip read times can beexpanded to include sub-second timing. TS-TS NET communication systemsand methods should properly handle time values that may include tenths,hundreds, or thousandths of a second.

In the TS system, the chip number is generally the same as the bibnumber worn by the participant. Thus, for an event with perhaps 500participants, the Bib # field may contain a value from 1 to 500. Forlarger racing events, the Bib # field can be up to 99999 or even up to500000 or so depending on the requirements as the TS and TS-TS NETsystems will support these expanded field lengths.

The following is a sample of a typical TS-TS NET output file using theHH:MM:SS format:

0,41,41,“14:27:42”

0,47,47,“14:27:44”

0,39,39,“14:27:46”

0,14,14,“14:27:48”

0,32,32,“14:27:50”

Each TS is capable of detecting and reading a single chip or participantmultiple times as it approaches a timing detection point. Thus, anoutput file may contain multiple entries for the same chip/participant.The last entry is the final read on a chip. For example, the followingoutput file shows that a single chip was read multiple times as therunner approached the finish line in an event.

0,32,32,“14:28:20”

0,32,32,“14:28:21”

0,32,32,“14:28:22”

In one exemplary embodiment, the output file only contains one entrysince most runners can pass through the detection point in one second orless. However, if an event can have a number of walkers, there mayeasily be 4 to 5 entries for the same timing chip as the walkerapproaches and goes past the finish line.

As an TS system or detection system reads timing chips, the TS systemappends new data to the file and continues to do so during the event.Thus, the file should not be modified or locked while an event or eventis ongoing. It's best to read the file once the event is concluded, orwhile the system is not actively reading timing chips.

Each TS system coupled with a location data system (LDS) can have ahigh-speed memory with a binary database that runs in the memory and isupdated very rapidly when the detection are made such as when chips arebeing read. When this database is saved to the disk drive, it is writtento a text file using a delimited format, such as delimited using commas.When using commas as the delimiters, the file can be read by third-partyprograms without having to build a complex database interface as suchfiles are common as known to those skilled in the art.

The following is a sample TS DATABASE file record:

1,Jay_Cooper,08:00:00,08:15:00,00:00:00,00:00:00,00:00:00,08:45:00,00:45:00,50,Half Marathon,M,Allentown,Team Cooper,50001,Club Member,#76435,137

TS can have the ability to automatically write out the TS DATABASE FILEduring an event to a file name selected by the TS user. For example, theTS can be specified to have a file written to the disk every 30, 45, orperhaps 60 seconds. In addition to writing the TS DATABASE FILE to thedisk, TS can automatically create multiple files that have a unique filename that is based on the current date and time. By having multiplefiles on the disk, any of the files can be accessed without a concernabout TS accessing those files again once they have been created. Forexample, an TS system can write the database to the disk every 60seconds with a unique file name. The TS system can specify the base filename as TSDB.txt. When TS writes the file, it creates a file with thefollowing name format:

TSDB20090501100502.txt

There can be multiple TS DATABASE FILES on the disk drive, and therecould be hundreds of files by the time the event completes. Each ofthese files is essentially a unique snapshot of the event results forthat moment in time.

The following is the format for the database file:

Bib#,Name,StartTime,Split1,Split2,Split3,Split4,FinishTime,ElapsedTime,Age,Division,Gender,City,TeamName,ChipField,UserField1,UserField2,UniqueID

The Bib # field can contain a value from 1 to 99999 depending on theversion of the TS system in use.

The Name can contain the full name and is typically formatted as FIRSTNAME LAST NAME with no comma between the first and last name, but may beformatted such as using an underscore or the like. In some embodiments,it is undesirable for particular characters, such as a comma, by way ofexample, not be included in the name field due to their use as adelimiter where applicable. When an TS system loads the database file,it can use particular characters such as a comma to determine theindividual fields. Thus, such TS database delineation characters shouldnot be used in the Name field as such usage can cause TS to use thewrong fields for the remaining entries on the line being read.

The following fields all contain a time based on the time of day: StartTime, Split1, Split2, Split3, Split4, Finish Time. All of these fieldsare in the format HH:MM:SS or HH:MM:SS.XXX and there are no quote marks.

The described format for chip read times can be expanded to includesub-second timing. Any TS-TS NET implementations should be implementedto properly handle time values that may include tenths, hundreds, orthousandths of a second. Following is one exemplary embodiment of a setof applicable TS data fields:

a) The Elapsed Time field is a calculated field which is typically theFinish Time minus the Start Time. This field is in the format HH:MM:SSor HH:MM:SS.XXX and there are no quote marks.

b) The Age field can contain up to 3 digits typically ranging from 1 to100.

c) The Division field can contain a text entry that can be up to 250characters in length, although it is typically 20 or less characterslong.

d) The Gender field can contain a text entry that can be up to 250characters in length, although it is typically 1 character with eitheran M or F entry.

e) The City field can contain a text entry that can be up to 250characters in length, although it is typically 25 or less characterslong.

f) The Team Name field can contain a text entry that can be up to 250characters in length, although it is typically 25 or less characterslong.

g) The Chip field can be used, in some embodiments, to include a textentry that is associated with a particular timing chip. In someembodiments the Chip field can be up to 250 characters in length,although it is expected to be 6 or less characters long.

h) The UserField1 field can contain a text entry that can be up to 250characters in length, although it is typically 25 or less characterslong. This field may be used by the software to contain values relatedto team order for relay events. In some cases, the TS user can placeinformation in this field related to the TS user's personal informationsuch as emergency contact number.

i) The UserField2 field can contain a text entry that can be up to 250characters in length, although it is typically 25 or less characterslong. This is a second field that often contains additional personalinformation about an event participant.

j) The UniqueID field can contain a text entry that can be up to 250characters in length, although it is typically 10 or less characterslong. This field is often used to track event-day registration numbersor other unique values that identify an event participant. TS canautomatically insert a unique value in this field during the rapidregistration process in the software.

Not only can TS write this TS DATABASE FILE text file to the disk drive,it can read it back in from the TS DATABASE FILE. Thus, a TS DATABASEFILE can be created using this format and TS can read it just fine. Anytime fields that are created should be in the HH:MM:SS or HH:MM:SS.XXXformat with leading zeros on any times that are less than 10. Forexample, if the time is 9:10 am, the field should contain the entry09:10:00 or 09:10:00:000. In most cases, when creating a new file thatcan be loaded into TS, the time fields should contain 00:00:00 or00:00:00:000. However, if an event has assigned start times, the starttimes can be loaded into TS by using the StartTime field.

TS can have a state-less network interface such as provided by a userdata protocol (UDP) system as used for outbound and inbound messagingover a suitable communication network. The TS-TS NET system utilizesthese messages to include outbound packets using TS-TS NET for READ andANNOUNCE information, as well as other data as described herein. Inaddition, an TS using TS-TS NET monitors the Internet connection for UDPTS-TS NET messages from other TS-TS NET systems or third-party programscoupled to the same communication network. This interface allowsthird-party programs to be developed which can work within the TSarchitecture.

UDP packets as used by the present TS-TS NET system provide a very quickand relatively easy system to implement and from which to build flexibleand robust applications. While there are known limitations for UDPpackets, the describes application of the UDP packets in the TS-TS NETrecognizes these limitations and adjusts the design and applicationsaccordingly whereby UDP provides a very suitable solution forcommunicating between multiple TS systems.

The following includes the packet structure for all TS-TS NET supportedUDP packets. TS-TS NET can be configured to listen and send on anysocket ranging from 5000 to 9999. In addition, TS-TS NET can be set tosend to a specific computer by using either the computer name or its IPaddress. Furthermore, TS-TS NET can send to all computers on the networkby using 0.255 as the last bytes in the IP address. Of course in othersystems and embodiments other broadcast messaging address can also beused and still be within the scope of the present invention. In thisexample, if the TS-TS NET is set to 192.168.1.255, the TS-TS NET sendsmessages as Broadcast packets. TS-TS NET message are sent as clear textcontained within the UDP packet, with fields separated by the “1”characters. |EOM| should always come at the end of each message.

As noted, the TS-TS NET network interface is configured for statelessbroadcast communications systems, such as UDP using a broadcasting IPaddress indicator such as 255. The networking interface can howeversupport a variety of different types of messages. These can includebroadcast messages, multicast messages and unicast messages, between andamong various TS-TS NET systems.

Broadcast TS-TS NET messages are transmitted from the TS-TS NETinterface over the stateless broadcast communication network with noaddressing as to the intended recipient as well as no identification theTS-TS NET system that is sending or sent the message. As such, each ofthe Broadcast TS-TS NET Messages can be read by any listening TS-TS NETdevice, and once received by that device, the receiving TS system doesnot know which other TS system sent the message. As will be discussed,these include, by way of example, the ANNCM and TRSTART messages.

Multicast TS-TS NET messages are transmitted from the TS-TS NETinterface over the stateless broadcast communication network with noaddressing as to the intended recipient. However, these messages includean identification of the sending TS system, e.g., FROM identifier. TheseTS-TS NET multicast messages can be read by any TS-TS NET system andonce received by that TS system, the receiving TS system knows which ofthe other communicating TS systems the message originated. Theseinclude, by way of example, the ANNC, ANNCL, READ, NOANNC, TSYNC, RSIG,and KREFRESH messages.

Unicast TS-TS NET messages are transmitted from the TS-TS NET interfaceover the stateless broadcast communication network with anidentification of which the sending entity is (FROM identifier) as wellas an identification of the intended receiving TS system (DEST orDestination identifier). These unicast TS-TS NET messages areessentially point to point messaging within a stateless broadcastmessaging communication system. Only the identified destination TS-TSNET system should receive these messages and they are ignored by allother listening TS system. The receiving TS system knows that themessage was intended for its use and it knows the identification of thesending TS. These include, by way of example, the REANNC, RESEND,LOOKUP, STARTRFID, STOPRFID, COMMAND, RQIMAGE, STIMAGE, RQIDIR, STIDIR,RQISTREAMON, and RQISTREAMOFF messages by way of example.

It should be understood to those skilled in the art that otherbroadcast, multicast and/or unicast messages can also be developed as anapplication may require or benefit from the present disclosure, andstill be considered within the scope of the present disclosure.

Announce Message (ANNC): The ANNC packet is sent by TS-TS NET to thenetwork and can be captured by any device that is listening on thenetwork for UDP packets. The message indicates that TS can have read achip at the location indicated in the From field.

Packet length=variable size

Total fields=10

ANNC|FROM|BIB#|NAME|AGE|GENDER|CITY|TIME|PACKET#|E OM|

The information in this TS-TS NET packet comes from the TS internaldatabase. The packet # is a unique 3-digit value that begins with 1 andcontinues to 999, after which it wraps around and starts over at 1. Thispacket # can be used to ensure that all messages are received. If amessage is missing, a request can be made to resent that packet. TS-TSNET maintains a circular buffer of past messages for this purpose.

Announce Message for Lap Events (ANNCL): The ANNCL packet is sent byTS-TS NET to the network and can be captured by any device that islistening on the network for UDP packets. The message indicates that TScan have read a chip at the location indicated in the From field.

Packet length=variable size

Total fields=11

ANNCL|FROM|BIB#|NAME|AGE|GENDER|CITY|TOTAL LAPS|TIME|TEAMNAME|PACKET#|EOM|

The information in this TS-TS NET packet comes from the TS internaldatabase. The packet # is a unique 3-digit value that begins with 1 andcontinues to 999, after which it wraps around and starts over at 1. Thispacket # can be used to ensure that all messages are received. If amessage is missing, a resend of the packet can be requested. TS-TS NETmaintains a circular buffer of past messages for this purpose.

Re-Announce Message (REANNC): The REANNC packet is sent by TS-TS NET torequest a re-send of a particular packet.

Packet length=variable size

Total fields=5

REANNC|FROM|DEST|PACKET#EOM|

When this TS-TS NET message is used, the packet number should beincluded as desired from the TS or TS-TS NET buffer. The FROM and DESTfields contain the IP addresses for the two systems.

No Announce Information (NOANNC): The NOANNC packet is sent via theTS-TS NET when a request was made for a packet that is not yetavailable. For example, if TS-TS NET can only send 100 packets, and asystem requests packet number 120, the system will generate the NOANNCmessage in response.

Packet length=variable size

Total fields=10

NOANNC|FROM|0| |0|M| |00:00:00|Packet #|EOM|

The message returns the requested packet number with the NOANNC header.

Announce Message Information (ANNCM): The ANNCM packet is sent by TS-TSNET or the Kiosk when a new message is received by an input such as isentered by a participant or family member requesting a specificparticipant's data be displayed on a Kiosk or an Announcer screen.

Packet length=variable size

Total fields=4

ANNCM|BIB #|MESSAGE|EOM|

Read Message (READ): The READ packet is sent by TS-TS NET to the networkand can be captured by any device that is listening on the network forUDP packets. The packet is a real-time feed of any reads that areoccurring at the particular TS timing system.

Packet length=variable size

Total fields=6

READ|FROM|BIB#|TIME|PACKET #|EOM|

Packet number is a value that begins with 1 and goes to 999. Once itreaches 999, it starts over again at 1. This packet number is used toreference past messages in case a message is lost on the network and are-send is requested.

Additionally a separate READ message can be used that includes thePARTICIPANTNAME field in lieu of the BIB#.

Resend Message (RESEND): The RESEND message is sent to any TS systemrequesting that it re-send a past message. If a message is lost over thenetwork, a request to resend can be made for any of the last 999messages sent previously. TS-TS NET maintains a buffer with the past 999messages. Once the 999 position is used, TS-TS NET starts over atposition 1. Thus, TS-TS NET is maintaining a circular buffer ofmessages.

Packet length=variable size

Total fields=5

RESEND|FROM|DEST|PACKET #|EOM|

The Destination field is the TS system that should respond to thisrequest. This is the same name set in the TS Defaults for “My Name” inthe networking section. If a request is made for a packet number thathas not yet been used by TS-TS NET, a packet response starting with theBLANK field can be received.

Time Sync Message (TSYNC): The TSYNC message is sent using TS-TS NET toany TS system that is listening for Time Sync commands. This istypically used by TS Remote to make sure the time on the Remote laptopis the same as that on the TS system. There can always be a slight delayin the network transmission, and as such a 0.25 to 0.5 second delay maybe added to the time received using TS-TS NET to compensate for thedelay.

Packet length=variable size

Total fields=4

TSYNC|FROM|TIME|EOM|

The FROM field is the name set in the TS Defaults as My Name.

Time Sync Message (TRSTART): The TRSTART message is sent using TS-TS NETto the Kiosk to set the start clock for the event. The start time can beset on a Kiosk using a command in the Configuration screen. However, bysending this packet to the Kiosk, the time can be set remotely from a TSsystem.

Packet length=variable size

Total fields=4

TSYNC|TIME|EOM|

Remote Signal Message (RSIG): The RSIG message is sent using TS-TS NETto any system that is listening for RSIG command. This is typically usedby TS Remote to make sure the connection over the network is good toTS-TS NET and also to verify that TS-TS NET is scanning and listeningfor remote entries.

Packet length=variable size

Total fields=4

RSIG|FROM|TIME|EOM|

The FROM field is the name set in the TS Defaults as My Name.

Refresh KIOSK Message (KREFRESH): The KREFRESH message is sent usingTS-TS NET to any system (typically a Kiosk) that is listening for theKREFRESH command. This is typically used by TS-TS NET to send out all ofthe results in an event to the Kiosk. This might be useful if the Kioskre-booted or if the Kiosk was started after results had already occurredin an event.

Packet length=variable size

Total fields=10

KREFRESH|FROM|BM#|NAME|AGE|GENDER|CITY|TIME|PACK ET#|EOM|

The information in this TS-TS NET packet comes from the TS internaldatabase. The packet # is a unique 3-digit value that begins with 1 andcontinues to 999, after which it wraps around and starts over at 1. Thispacket # can be used to ensure that all messages are received. If amessage is missing, a request that packet be re-sent can be made. TS-TSNET maintains a circular buffer of past messages for this purpose.

Lookup Message (LOOKUP): The LOOKUP message allows a device to requestevent information from another device. The identifier may be any text.In most cases, the identifier will be a tag serial number, event bibnumber, participant name, or perhaps a unique identifier that refers toa particular type of information. For example, if a TS systems needs toknow the current duration of an event, the LOOKUP message could be sentto a TS system that is responsible for tracking the total event time.The identifier field might contain the text entry “EVENTTIME” and thisentry could be used to indicate that the event duration is desired. Thepacket number field is optional and if not used, the field could containa single space.

Packet length=variable size

Total fields=6

LOOKUP|FROM|DEST|IDENTIFIER|PACKET #|EOM|

Start RFID Message (StartRFID): The StartRFID message is sent to a TSsystem to indicate that it should start performing a specific RFIDfunction. If the function is to begin at a certain date or time, theTIME field could contain that information. This field could be used toinitialize and start a remote RFID system so that it begins to readtags. As also, as used here this is specific to RFID readers. It shouldbe understood to those skilled in the art, that other reader ordetection systems are possible and in such embodiments, other messagescan be developed or this message can be adapted for their use. Othersystems could include: laser detection, video detection, etc. As such,this message could alternatively be: StartDETECTOR, or StartLASER, orStartVIDEO. by ways of examples.

Packet length=variable size

Total fields=7

StartRFID|FROM|DEST|FUNCTION|TIME|PACKET #|EOM|

Of course those skilled in the art will understand that when othertechnology is used for the tag reader or participant detection system,this message can be renamed and still be within the scope of the presentdisclosure.

Stop RFID Message (StopRFID): The StopRFID message is sent to a deviceto indicate that it should start performing a specific RFID function. Ifthe function is to begin at a certain date or time, the TIME field couldcontain that information. This field could be used to initialize andstart a remote RFID system so that it begins to read tags. Other systemscould include: laser detection, video detection, etc. As such, thismessage could alternatively be: StopDETECTOR, or StopLASER, orStopVIDEO. by ways of examples.

Packet length=variable size

Total fields=7

StopRFID|FROM|DEST|FUNCTION|TIME|PACKET #|EOM|

Of course those skilled in the art will understand that when othertechnology is used for the tag reader or participant detection system,this message can be renamed and still be within the scope of the presentdisclosure.

Command Message (COMMAND): The COMMAND message is sent to a TS system torequest that a particular command be executed in that TS system. TheIDENTIFIER field may contain any text desired. This field could be usedto send any tag reader or participant or tag detector command to aremote device. For example, if the current battery charge level on aremote system needed to determined, a Command message could be sent withthe text BATTERYSTATS in the IDENTIFIER field. The remote system wouldneed to have functions built in that can process the command.

Packet length=variable size

Total fields=6

COMMAND|FROM|DEST|IDENTIFIER|PACKET #|EOM|

Request Image Message (RQIMAGE): The RQIMAGE message is sent to a deviceto request that a particular image be returned. The message is usefulwhen interfacing with a system that contains photographs or otherpictures such as logos or artwork. The IDENTIFIER field should contain aunique descriptor for the image desired and may contain any textdesired. Typically, this field will contain a unique number for aparticipant in an event. However, the IDENTIFIER could also contain aspecific location on a remote system where a file is located. TheCOMPRESSION field may be used to specify the format of the image to besent. If higher performance across a network is desired, this fieldmight be used to indicate that High compression is desired. The fieldmay contain any text that is recognized by the system designated asDEST. The PACKETSIZE field should contain a value indicating the maximumpacket size to send at one time. Given that most images will containmore data than is able to be sent in a single packet, this field may beused to control packet size, thus tuning the network performance. ThePSOCKET field is used when it necessary or desired to have multiplepacket streams being sent simultaneously from the DEST. For example, thefield could contain 7000 on one packet and 7001 on a different packet toindicate that two streams are being used simultaneously.

Packet length=variable size

Total fields=9

RQIMAGE|FROM|DEST|IDENTIFIER|COMPRESSION|PACKETSIZE|PSOCKET|PACKET#|EOM|

Image Sent Message (STIMAGE): The STIMAGE message is sent from a systemresponding to a request for an image, e.g., RQIMAGE. The IDENTIFIERfield should contain the unique descriptor for the image that wasrequested and may contain any text desired. Typically, this field willcontain a unique number for a participant in an event. However, theIDENTIFIER could also contain a specific location on a given systemwhere a file is located. The COMPRESSION field indicates the type ofcompression used on the image when it was sent. If higher performanceacross a network is desired, this field might be used to indicate thatHigh compression is desired. The PACKETSIZE field should contain a valueindicating the length of the portion of the image just sent. Given thatmost images will contain more data than is able to be sent in a singlepacket, this field will be used to indicate how many bytes have beensent. The PSOCKET field contains a value indicating which stream theinformation is being sent on. This may be used when it necessary ordesired to have multiple packet streams being sent simultaneously from asystem. For example, this field could be used to send individual photosto different computers on a network at the same time.

Packet length=variable size

Total fields=9

STIMAGE|FROM|DEST|IDENTIFIER|COMPRESSION|PACKETSIZE|PSOCKET|PACKET#|EOM|

Request Image Library Contents Message (RQIDIR): The RQIDIR messagecould be sent to a device to request that the names of all imagesavailable be provided for that system. The message is useful wheninterfacing with a system that contains photographs or other picturessuch as logos or artwork. The IDENTIFIER field should contain a uniquedescriptor for the type of images desired or a filter mask for the namesor locations of images. For example, the IDENTIFIER might contain thetext entry *, or it might contain a qualifier such as *.JPG is the useronly wants to receive a list of images that are in JPG format. Of courseother qualifiers may be used for other formats.

Packet length=variable size

Total fields=6

RQIDIR|FROMDEST|IDENTIFIER|PACKET #|EOM|

Image Library Sent Message (STIDIR): The STIDIR message is sent to oneor more systems as a response to an RQIDIR message and it includes alist of images available. The FILELIST field will contain a list ofimages in text format that are available. Each image name will contain acarriage return line feed indicator at the end of the name. If the listhas been completely transmitted, a final indicator at the end of thelist will include an entry of EOL followed by a carriage return linefeed. This indicator means there are no additional packets being sentand the entire list has been provided.

Packet length=variable size

Total fields=6

STIDIR|FROMDEST|FILELIST|PACKET #|EOM|

Request Image Message (RQISTREAMON): The RQIDTREAMON message is by a TSsystem to request that a particular image stream be enabled for areal-time video feed. The message is useful when interfacing with asystem that contains a camera displaying live video. The IDENTIFIERfield should contain a unique descriptor for the image stream desiredand may contain any text desired. Typically, this field will contain aunique name for a camera or video interface. However, the IDENTIFIERcould also contain a specific socket, URL, or other indicator that is alive video stream. The COMPRESSION field may be used to specify theformat to be used when sending the video stream. If higher performanceacross a network is desired, this field might be used to indicate thatHigh compression is desired. The field may contain any text that isrecognized by the system designated as DEST. The PACKETSIZE field shouldcontain a value indicating the maximum packet size to send at one time.Since the video stream will contain a great amount of information, theimage stream can be deconstructed into small packets that are sentacross the network. The PSOCKET field is used when it necessary ordesired to have multiple packet streams being sent simultaneously fromthe DEST. For example, the field could contain 6000 on one packet and6001 on a different packet to indicate that two streams are being usedsimultaneously. The TIMEOUT field can be used to indicate how long, inseconds, the stream should be kept alive. If this value is set to 0, theDEST will continue to send the stream until a RQISTREAMOFF message isreceived.

Packet length=variable size

Total fields=10

RQISTREAMON|FROM|DEST|IDENTIFIER|COMPRESSION|PACKETSIZE|PSOCKET|TIMEOUT|PACKET #|EOM|

Request Image Message (RQISTREAMOFF): The RQISTREAMOFF message is sentby a TS system to a request that a particular image stream be disabled.The IDENTIFIER field should contain a unique descriptor for the streamto be disabled. The PSOCKET field can also be used to identify aparticular socket, in the event that multiple streams are being sent atthe same time.

Packet length=variable size

Total fields=7

RQISTREAMOFF|FROM|DEST|IDENTIFIER|PSOCKET|PACKET #|EOM|

In other embodiments, the packet formats can vary from that describedabove and herein and still be within the scope of the presentdisclosure. For example, some or all of the timing system databasefields is sent when most of the packets are sent. In such embodiments,this can allow applications to have all of the data contained in arecord in the database.

GPS Wakeup Message (GPSWAKE): The GPSWAKE message is sent to by a TSsystem to a TS or TRS system or GPS chip to request that a communicationsession begin related to a GPS read or determination. Receipt of thismessage by a GPS enabled GPS chip or GPS chip reader system (TRS) tosend back parameters for the session in the buffer that sensed andreceived the GPS data from the GPS chip. The LSOCKET value can be usedto identify a unique socket being used for the session. The SETTINGSvalue is used to request the TS or TRS conform to specific parametersfor the session. Once a session is established, the requesting entitywill wait for data to show up in the buffer and process it accordingly.Thus, this message is sent to a GPS enabled TRS when setting up along-term session where GPS read data will trickle in over time, intothe Buffer allocated.

Packet length=variable size

Total fields=7

GPSWAKE|FROM|DEST|SOCKET|SETTINGS|BUFFER|EOM|

GPS Wakeup and Receive Message (GPSRWAKE): The GPSRWAKE message is sentto TS or TRS system or GPS chip to request that a communication sessionbegin with GPS data being returned immediately. This message causes theGPS enabled chip or GPS enabled TRS system to send back GPS location andpossibly also the time information in the GPS reader or TRS systemhaving received the message and having had at least one GPS chip beingdetected by such system. The LSOCKET value can be used to identify aunique socket being used for the session. The SETTINGS value is used torequest the TS or TRS system conform to specific parameters for thesession. Once the initial data has been received by the requestingentity, the session will remain open and wait for additional data toappear in the buffer of the requested entity. This command differs fromthe GPSWAKE message since the GPSWAKE does not request data, but onlyactivates the GPS enabled TRS system to wait for the next available GPSread data, when it occurs, e.g., the GPSWAKE message waits for data toshow up. In contrast, the GPSRWAKE message requests that all GPS data besent immediately by the receiving entity, thus clearing the buffer ofthe receiving entity such as a GPS enabled TRS or the GPS enable chipitself.

Packet length=variable size

Total fields=7

GPSRWAKE|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Receive Message (GPSRMESS): The GPSRMESS message is sent to TS orTRS system or GPS chip for GPS chip data reading to request that alldata be transmitted immediately by the receiving system. This is astateless message that does not require a session to first be createdbetween the requesting and receiving entities. Therefore, the GPSRMESSmessage can be used in situations where rapid communications with a GPSor SGOS TRS system requires, such as a verification of a prior read orin a situation the requesting TS system determines from other facts orfactors. The LSOCKET value can be used to identify a unique socket beingused to receive the data. The SETTINGS value is used to request the TSor TRS system to conform to specific parameters for the datatransmission. BUFFER will contain the actual data coming back to thecaller.

Packet length=variable size

Total fields=7

GPSRMESS|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Re-Send Message (GPSRSMESS): The GPSRSMESS message is sent to a TSor TRS system or GPS chip to request that the data previously sent, bere-transmitted. This message can be used to retrieve data that may havebeen lost in route from the requested entity (another TS or TRS systemor GPS chip) to the requesting entity such as another TS. This is astateless message that does not require a session to first be created.Thus, it is ideal for rapid communications with a chip or system. TheLSOCKET value can be used to identify a unique socket being used toreceive the data. The SETTINGS value is used to request the chip orremote system conform to specific parameters for the data transmission.BUFFER will contain the actual data coming back to the caller.

Packet length=variable size

Total fields=7

GPSRSMESS|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Waypoint Message (GPSWAYP): The GPSWAYP message is sent to a chip orremote system to request specific data that is based on a specific orrange of waypoint values. This is a stateless message that does notrequire a session to first be created. Thus, it is ideal for rapidcommunications with a chip or system. The LSOCKET value can be used toidentify a unique socket being used to receive the data. The SETTINGSvalue is used to request the chip or remote system conform to specificparameters for the data transmission. BUFFER will contain the actualdata coming back to the caller.

Packet length=variable size

Total fields=7

GPSWAYP|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Send Message (GPSSENDS): The GPSSENDS message is sent to another TSor TRS system or GPS chip to transmit GPS data be sent immediately. Thismessage requires you to first create a session. The TSOCKET value can beused to identify a unique socket on the remote system. The SETTINGSvalue is used to request the chip or remote system conform to specificparameters for the data reception. BUFFER will contain the actual databeing sent. The advantage to using the GPSSENDS message is that theremote system will automatically handle error handling for lost messagesthat did not arrive.

Packet length=variable size

Total fields=7

GPSSENDS|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Send Message (GPSSENDC): The GPSSENDC message is sent to a TS or TRSsystem or GPS chip to transmit data immediately. This message does notrequire a session. The TSOCKET value can be used to identify a uniquesocket on the remote system. The SETTINGS value is used to request thechip or remote system conform to specific parameters for the datareception. BUFFER will contain the actual data being sent.

Packet length=variable size

Total fields=7

GPSSENDC|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Close Message (GPSCLOSE): The GPSCLOSE message is sent to anotherTS, or TRS system or GPS chip to inform it that transmissions regardingGPS location data are now over and the sockets being used for GPSlocation data have been released. The TSOCKET value can be used toidentify a unique socket on the remote system. This message is used forsessions that are always open as described above, for example, GPSWAKE,GPSRWAKE.

Packet length=variable size

Total fields=5

GPSCLOSE|FROM|DEST|LSOCKET|EOM|

The GPSSENDC is used to send data to another system, which could be anydevice including a laptop computer, network file server, or another RFIDreader. We also have the GPSSENDS message as well. The only differenceis that the GPSSENDS message is used for session-oriented communicationswhere the remote system is able to process packets and look for errorsthat can cause it to send a message back letting the sender know thatthe data didn't arrive correctly. The GPSSENDC doesn't require a sessionand it looks like a UDP datagram and is a connectionless packet. Thismakes it faster and easier to work with, but it doesn't have any builtin error correction.

The buffer field contains information related to the GPS data. In fact,the buffer could also contain RFID information as well. For example, abasic message buffer might have something like the following GPSnumber,Total Satellites, Uptime, Longitude, Latitude, Offset, Current Time, andElevation. The buffer is free-form text meaning the user can implementtheir own formatting within the buffer to determine delimiters betweenthe data elements. As an example, a TS might use the # character todesignate the end of each field within the buffer. Thus, I might have apacket that has a buffer containing something like:34.56575#121.456487#18:00:03#0.564#234

Any known GPS receiver ID can also be transmitted with the GIS locationdata.

In one embodiment, the GPS data is sent without waiting for the remotesystem to setup a connection socket. This is because in futureimplementations, we will be using multiple VPN ports to send messagesback to ITS or perhaps any other system. Presently, the system here atITS listens for any and all messages on a common socket. Soon we willallow the user to designate a socket in real-time as they wish to havedata sent to a system. The GPSSENDC message will be used for thatpurpose and when the receiving system collects a packet with theGPSSENDC header, it will parse the buffer to look for specificinformation regarding the desired communication parameters coming fromthe sender.

One example, of the waypoint message GPSWAYP, is where there may be atiming point along the course needs to collect data from the chips onthe runners and the race has 50,000 participants in it. Now assume thistiming point is at mile 5. There will be thousands of runners comingthrough that timing point very rapidly, thus the density will be veryhigh. If the TS tried to collect every GPS data point from them, itwould take a while (relative term) to collect the data for every 2 feetof resolution. During the first part of the race, it is less likely toneed or track the runner's position every 2 to 3 feet. Most situationsyou can have data for every 50 to 100 feet. Thus, this message GPSWAYPallows the TS to tell the chip on the runner that we don't need all ofthe data, just a portion of it. The communications are much faster thatway and we can handle very large densities of runners. The Settings is afree-form field that can be customized by the user. However, it is alsopossible to send a message such as:GPSWAYP|FROM|DEST|LSOCKET|Res:10|BUFFER|EOM| The value of Res:10 couldmean to send us the data point for every 10 seconds from the GPSinformation collected. Thus, let's say the runner was on the course sofar for 20 minutes and this is the first time we are collected thepositional data, we will be asking for 6 samples per minute×20minutes=120 pieces of data. A GPS receiver can provide data down to100th of a second and thus if we simply requested all data, we mighthave thousands of data points and that would take a long time to sendfrom the runner's chip to the timing system. So, the GPSWAYP messageallows the TS to decide how much data it will need and this can bechange changed in real-time based on the density of runners the TS isseeing from the GPS reads.

The process of sending an acknowledgement could also be added. Thiscould be something like GPSACK: GPSACK|FROM|DEST|LSOCKET|BUFFER|EOM

In other embodiments, he process of sending an ACK requires more roundtrip time, which is not good when dealing with high densities ofpackets. This is much like the old UDP vs. TCP/IP argument. TCP/IP hasthe advantage of being a session protocol that has error correctionthrough ACKs. UDP is much faster for sending bulk data because itrequires no ACK. For the TS, it may be desirable to dump the locationdata rapidly to a TRS, LDS or TS without having the overhead of theACKs. So, I think it would make sense to go ahead and add the ACKmessage in our spec. Thus, here is the format we will use:

The buffer will contain a response code which will likely be a value of0 for failure and 1 for success. The TS could also use other values suchas 2 or 3 for error handling.

In another embodiment a display system or remote monitoring system maywant to display something like a moving map image of where the runnerhas been. In such embodiments, the remote system can send a GPSRMESSmessage to a file server or database or computing device that has storedall of the GPS data for one or more participants. When the message issent over, the buffer will contain identifying data for determining whatwill be sent back to the requesting system. So, the requesting system,such as Announcer, may have something like the following in the buffer:REQALLGPSDATA:543. This could mean that system wants all GPS data storedin a database for bib number 543. In other cases, the remote systemcould also send the following in formation in the buffer:REQTIMERANGEGPSDATA:543 and that might mean to send over all data withina time range for bib 543.

Operating Environment

Referring to FIG. 10, an operating environment for an illustratedembodiment of the TS Location Tracker or TS system is a computer system700 with a computer 702 that comprises at least one high speedprocessing unit (CPU) 704, in conjunction with a memory system 706interconnected with at least one bus structure 708, an input device 710,and an output device 712. These elements are interconnected by at leastone bus structure 708. As addressed above, the input and output devicescan include a communication interface including an antenna interface.

The illustrated CPU 704 for an RFID semiconductor chip is of familiardesign and includes an arithmetic logic unit (ALU) 714 for performingcomputations, a collection of registers for temporary storage of dataand instructions, and a control unit 716 for controlling operation ofthe computer system 700. Any of a variety of processors, including atleast those from Digital Equipment, Sun, MIPS, Motorola, NEC, Intel,Cyrix, AMD, HP, and Nexgen, is equally preferred but not limitedthereto, for the CPU 704. The illustrated embodiment of the inventionoperates on an operating system designed to be portable to any of theseprocessing platforms.

The memory system 706 generally includes high-speed main memory 720 inthe form of a medium such as random access memory (RAM) and read onlymemory (ROM) semiconductor devices that are typical on an RFIDsemiconductor chip. However, the present disclosure is not limitedthereto and can also include secondary storage 722 in the form oflong-term storage mediums such as floppy disks, hard disks, tape,CD-ROM, flash memory, etc. and other devices that store data usingelectrical, magnetic, and optical or other recording media. The mainmemory 720 also can include, in some embodiments, a video display memoryfor displaying images through a display device (not shown). Thoseskilled in the art will recognize that the memory system 706 cancomprise a variety of alternative components having a variety of storagecapacities.

Where applicable, while not typically provided on RFID tags or chips, aninput device 710, and output device 712 can also be provided. The inputdevice 710 can comprise any keyboard, mouse, physical transducer (e.g. amicrophone), and can be interconnected to the computer 702 via an inputinterface 724 associated with the above described communicationinterface including the antenna interface. The output device 712 caninclude a display, a printer, a transducer (e.g. a speaker), etc., andbe interconnected to the computer 702 via an output interface 726 thatcan include the above described communication interface including theantenna interface. Some devices, such as a network adapter or a modem,can be used as input and/or output devices.

As is familiar to those skilled in the art, the computer system 700further includes an operating system and at least one applicationprogram. The operating system is the set of software that controls thecomputer system's operation and the allocation of resources. Theapplication program is the set of software that performs a task desiredby the user, using computer resources made available through theoperating system. Both are typically resident in the illustrated memorysystem 706 that may be resident on the RFID semiconductor chip.

In accordance with the practices of persons skilled in the art ofcomputer programming, the present invention is described below withreference to symbolic representations of operations that are performedby the computer system 700. Such operations are sometimes referred to asbeing computer-executed. It will be appreciated that the operations thatare symbolically represented include the manipulation by the CPU 704 ofelectrical signals representing data bits and the maintenance of databits at memory locations in the memory system 706, as well as otherprocessing of signals. The memory locations where data bits aremaintained are physical locations that have particular electrical,magnetic, or optical properties corresponding to the data bits. Theinvention can be implemented in a program or programs, comprising aseries of instructions stored on a computer-readable medium. Thecomputer-readable medium can be any of the devices, or a combination ofthe devices, described above in connection with the memory system 706.

When describing elements or features and/or embodiments thereof, thearticles “a”, “an”, “the”, and “said” are intended to mean that thereare one or more of the elements or features. The terms “comprising”,“including”, and “having” are intended to be inclusive and mean thatthere may be additional elements or features beyond those specificallydescribed.

Those skilled in the art will recognize that various changes can be madeto the exemplary embodiments and implementations described above withoutdeparting from the scope of the disclosure. Accordingly, all mattercontained in the above description or shown in the accompanying drawingsshould be interpreted as illustrative and not in a limiting sense.

It is further to be understood that the processes or steps describedherein are not to be construed as necessarily requiring theirperformance in the particular order discussed or illustrated. It is alsoto be understood that additional or alternative processes or steps maybe employed.

1. A system for determining and tracking a location of a participanttracked with a RFID tag having a unique RFID tag number during an eventusing a timing system communicatively coupled to an RFID tag readersystem, the tag reader system is configured to be located at a fixedlocation in proximity to the route at a first monitored location pointfor receiving one or more tag reads from the RFID tag as the trackedparticipant with the RFID tag travels in proximity to said locationalong the route, and configured for determining a time for each tagread, identifying the tag number of the RFID tag, and transmitting a tagread message including at least a portion of the received tag reads withthe RFID tag number and the determined tag read time, the timing systemconfigured for receiving and storing the transmitted tag read messageincluding the tag number and the determined tag read times astransmitted by the tag reader system, wherein the participant has alocation device configured for associated with the participant, thelocation device configured to receive a plurality of location data asthe participant travels along the route, time stamping each receivedlocation data, and transmitting location information including theplurality of location data and the time stamps over the wirelesscommunication interface said system comprising: a location detectiondevice configured to be located at a fixed location in proximity to theroute at a second monitored location point and configured to be inwireless communication with the location device and configured forreceiving the transmitted location information from the location device;wherein the timing system stores the received location informationincluding the time stamps and associates the received locationinformation with the RFID tag number of at least one of the one or moretag reads of the received tag read message as a function of the tag readtimes and the time stamps of the location information, the timing systemdetermining a plurality of tracked locations of the participant alongthe route of the event as a function of the plurality of location dataand time stamps provided by the location information that is associatedwith the tag number for the participant.
 2. The system of claim 1wherein the location device is configured to include the RFID tag numberof the associated RFID tag for the participant and the locationinformation includes the RFID tag number.
 3. The system of claim 1wherein location device is configured for storing location data in amemory at intervals based on a predetermined rate.
 4. The system ofclaim 3 wherein the location device is configured to receive programminginstructions for establishing the predetermined rate, and wherein suchpredetermined rate can change with the receipt of new programminginstructions during the event.
 5. The system of claim 1 wherein thelocation device and the RFID tag are each configured to be carried on abody part of the participant, and wherein the location device is notcommunicatively coupled to the RFID tag.
 6. The system of claim 1wherein the location device is configured to receive a location datadownload request from the location detection device based on a downloadlocation command, and wherein the location device is configured totransmit the location information to the location detection device isconfigured to be responsive to said received location download request.7. The system of claim 1 wherein the location device is configured toonly transmit the received location data responsive to the locationdetection device receiving an input that a transmission to the locationdetection device is currently available.
 8. The system of claim 1wherein the timing system is configured to transmit to a remote system,before, during and after the event the plurality of tracked locationsassociated with a particular RFID tag number responsive to a the timingsystem receiving a request for participant specific location data thatincludes the particular RFID tag number from the remote system.
 9. Thesystem of claim 8, further comprising the remote system selected fromthe group consisting of a Kiosk, a website, a mobile phone, a mobilecomputing device, a portable computer, a tablet, a watch, a newsstation, or a broadcast network, the remote system being configured totransmit the request for the participant specific location data and theparticular RFID tag number to the timing system, to receive theparticipant specific location data in the form of the plurality oftracked locations as transmitted by the timing system, and to displaythe received plurality of tracked locations based on the receivedlocation data for the particular RFID tag number on a display map of theroute indicating the route traveled by the participant or the mostrecent and current location of the participant.
 10. The system of claim1 wherein the location device is configured for selective activation anddeactivation of a wireless location data receiver, and wherein awireless communication interface of the location device is configured toreceive activation and deactivation commands, and wherein the locationdetection device is configured for transmitting the activation anddeactivation commands responsive to a message received from the timingsystem.
 11. The system of claim 1 wherein the location detection deviceis configured to transmit to the location device a location data requestrequesting all or a portion of the stored location data from thelocation device when the location device is configured to be inproximity to the location detection device, and wherein the locationdevice is configured to transmit the requested location data responsiveto the received location data request.
 12. The system of claim 11wherein the location detection device is configured to transmit a dumpall data command and then transmit a clear all data command when thelocation device is in proximity to the location detection device, andwherein the location device is configured to transmit all of the storedlocation data and then clear the location data responsive to receipt ofthe dump all data command and then transmit a clear all data commandfrom the location detection device.
 13. The system of claim 1 whereinthe location providing source is a plurality of global positioningsystem (GPS) satellites and wherein the location data is GPS positiondata.
 14. The system of claim 1 wherein the location providing source isa plurality of wireless transmitters from a cellular network, andwherein the location data is cellular triangulation position data.
 15. Amethod for determining and tracking a location of a participanttraveling along a route wherein the participant being tracked with aRFID tag during an event using a timing system communicatively coupledto an RFID tag reader system, the tag reader system configured to belocated at a fixed location in proximity to the route at a firstmonitored location point for receiving one or more tag reads from theRFID tag as the tracked participant with the RFID tag travels inproximity to said location along the route, and configured fordetermining a time for each tag read, identifying the tag number of theRFID tag, and transmitting a tag read message including at least aportion of the received tag reads with the RFID tag number and thedetermined tag read time, the timing system configured for receiving andstoring the transmitted tag read message including the tag number andthe determined tag read times as transmitted by the tag reader system,the tag reader system configured for receiving one or more RFID tagreads from the RFID tag as the tracked participant with the RFID tagtravels the route, determining a time for each tag read, identifying thetag number of the RFID tag, and transmitting a tag read messageincluding at least a portion of the received tag reads with the tagnumber and the determined times, the timing system configured forreceiving the tag read messages as transmitted by the tag reader systemand storing the tag read message including the tag number from the tagreader system, the method for use with location device that isconfigured to be associated with the RFID tag of the participant andconfigured for: receiving a plurality of location data from a locationproviding source; time stamping each received location data; andtransmitting location data including the time stamps for each the methodcomprising: in a location detection device configured to be located at afixed location in proximity to the route and in wireless communicationwith the location device: receiving the transmitted location data; andtransmitting the received location data to the timing system; in thetiming system: receiving the location data including the plurality oflocation data and time stamps; associating the location data with theRFID tag number as provided by the RFID tag reader system from at leastone of the tag reads from the tag associated with the location device;determining a plurality of tracked locations of the participant alongthe route of the event as a function of the plurality of location dataand time stamps provided by the location information that is associatedwith the at least one tag read number for the participant storing theplurality of location data associated with the RFID tag number.
 16. Themethod of claim 15 wherein in the location device, the storing oflocation data is at intervals based on a predetermined rate.
 17. Themethod of claim 16 wherein in the location device, receiving programminginstructions for establishing the predetermined rate, and wherein suchpredetermined rate can be changed with the receipt of new programminginstructions during an event.
 18. The method of claim 15 wherein in thelocation device, receiving a location data download request, andtransmitting the tag location to a location detection device configuredto be is responsive to said request.
 19. The method of claim 15, whereinin at least one of the timing system and the tag reader system:detecting a proximity of the RFID tag to the RFID tag reader system; andtransmitting a location data download command to the location detectiondevice, wherein in the location detection device, transmitting thelocation data download request to the location device.
 20. The method ofclaim 15 wherein in the location detection device, the transmitting isonly responsive to the location detection device receiving an input thata transmission to the location detection device is currently available.21. The method of claim 15 wherein in the timing system, transmittingthe location data associated with a particular RFID tag numberresponsive to a request from a remote system.
 22. The method of claim15, wherein in a remote system selected from the group consisting of aKiosk, a website, a mobile phone, a mobile computing device, a portablecomputer, a tablet, a watch, a news station, or a broadcast network;requesting location data from the timing system for the particular RFIDtag number; and receiving the requested location data in the form of theplurality of tracked locations as transmitted by the timing system, anddisplaying the plurality of tracked locations as transmitted by thetiming system on a display map of the route indicating the routetraveled by the participant associated with the particular RFID tagnumber or the most recent and current location of the participantassociated with the particular RFID tag number.
 23. The method of claim15 wherein in the location detection device: transmitting at least oneof an activation and a deactivation command responsive to a messagereceived from the timing system; wherein in the location device:selectively activating and deactivating a location data receiverresponsive to receipt of the message from the location detection device.24. The method of claim 15 wherein in the location detection devicetransmitting to the location tag a location data request requesting allor a portion of the location data from the location device, and whereinin the location device transmitting the location data responsive to thelocation data request.
 25. The system of claim 15 wherein in thelocation detection device transmitting a dump all data command and thentransmitting a clear all data command, and wherein in the locationdevice, transmitting all of the location data responsive to the receiptof the dump all data command and clearing a memory of all location dataresponsive to receiving the clear all data command.